Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed classy finding #372

Open
wants to merge 1 commit into
base: 3.6
Choose a base branch
from

Conversation

ThomasTram
Copy link

resolves #371

@ThomasTram ThomasTram force-pushed the 371-fix-classy-finding branch from c8ce40b to 6a08012 Compare April 26, 2024 07:37
@ThomasTram ThomasTram force-pushed the 371-fix-classy-finding branch from 6a08012 to 2f1eb26 Compare April 26, 2024 08:53
@schoeneberg
Copy link

Just wanted to add that the newest classy can also install itself into the user's site-packages, so providing an explicit cosmo path is very weird for that. The solution should be as simple as allowing for
data.path['cosmo'] = 'detect'
or something like that, and then simply trying to import classy without verifying the location (maybe printing a warning/info to the user which classy is finally being picked). That'd be much nicer than the user having to list their site-packages directory inside of the data.path['cosmo'].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Finding classy is broken in several ways
2 participants